This chapter contains diagrams and configuration parameter tables for several of the examples of TN3270E server network configurations in Chapter 12, "TN3270E Server". The parameter values shown are from real working test configurations.
For an explanation of the columns and conventions in the configuration parameter tables, see Example Configuration Table Conventions.
The Network Utility World Wide Web pages contain binary configuration files that match these configuration parameter tables. To access these files, follow the Download link from:
http://www.networking.ibm.com/networkutility
The configurations documented in this chapter are:
Table 13-1. Cross-Reference of Example Configuration Information
Configuration Description | Parameter Table |
---|---|
TN3270 via a Subarea Connection to an NCP | Table 13-2 |
Highly Scalable, Fault-Tolerant TN3270E, for the TN3270 server TN A | Table 13-3 |
Highly Scalable, Fault-Tolerant TN3270E, for the Network Dispatcher ND A | Table 13-4 |
TN3270 Via DLUR over APPN | Table 13-6 |
Dynamic Definition of Dependent LUs | Dynamic Definition of Dependent LUs |
TN3270 Host Initiated Dynamic LU Definitions | Host Initiated Dynamic LU Definition |
TN3270 Host On-Demand Client Caching | TN3270E Host On-Demand (HOD) Client Cache |
TN3270 Subarea SNA over DLSw | TN3270E Subarea SNA over DLSw |
Figure 13-1. TN3270E Subarea
View figure.
See page "TN3270 via a Subarea Connection to an NCP" for a description and Figure 13-1 for a diagram of this configuration. | |||
Configuration Program Navigation |
Configuration Program Values |
Command-Line Commands |
Notes |
---|---|---|---|
Devices Adapters Slots |
Slot1: 2-Port TR |
See "add dev" on next row |
1 |
Devices Adapters Ports |
Slot 1/Port 1: Interface 0: TR |
Config>add dev tok |
2 |
Devices Interfaces |
Interface 0 MAC Address 400022AA0001 |
Config>net 0 TKR Config>set phy 40:00:22:AA:00:01 |
|
System General |
System name: NU_A Location: XYZ Contact: Administrator |
Config>set host Config>set location Config>set contact |
|
System SNMP Config General |
SNMP (checked) |
Config>p snmp SNMP Config>enable snmp |
|
System SNMP Config Communities General |
Community name: admin Access type: Read-write trap Community view: All |
SNMP Config>add community SNMP Config>set comm access write |
3 |
Protocols IP General |
Internal address: 172.128.252.2 Router ID: 172.128.1.2 |
Config>p ip IP Config>set internal 172.128.252.2 IP Config>set router-id 172.128.1.2 |
|
Protocols IP Interfaces |
Interface 0 (TR slot 1 port 1) IP address: 172.128.1.2 Subnet mask: 255.255.255.0 |
IP Config>add address |
|
Protocols IP OSPF General |
OSPF (checked) |
Config>p ospf OSPF Config>enable ospf (Accept other defaults) |
|
Protocols IP OSPF Area Configuration General |
Area number: 0.0.0.0 Stub area (not checked) |
OSPF Config>set area |
|
Protocols IP OSPF Interfaces |
Interface 0 OSPF (checked) |
OSPF Config>set interface Interface IP address: 172.128.1.2 Attaches to area: 0.0.0.0 (Accept other defaults) |
|
Protocols APPN General |
APPN network node (checked to enable) Network ID: NUBNODE Control point name: CPNU |
Config>p appn APPN config> set node Enable APPN Network ID: NUBNODE Control point name: CPNU(Accept other defaults) |
4 |
Protocols APPN Interfaces |
(highlight Interface 0 Token Ring) (click on the configure tab) Define APPN port (checked to enable) Port name: TR3270 High performance routing (HPR) supported (unchecked to disable) Support multiple PUs (checked to enable) |
APPN config>add port APPN Port Link Type: TOKEN RING Port name: TR3270 Enable APPN Support multiple PUs High performance routing: No (Accept other defaults) |
5 |
Protocols APPN Interfaces |
(highlight Interface 0 Token Ring) (click on the Link stations tab) STAT001 (new definition) General-1 Tab: Link station name: STAT001 Solicit SSCP session (checked) Link support APPN functions (unchecked) General-2 Tab: MAC address of adjacent node: 400000003172 Node ID: 12244 Local SAP address: 04 (click on Add to create the Link station)
|
APPN config>add link Port name for the link station: TR3270 Station name: STAT001 MAC address of adjacent node: 400000003172 Solicit SSCP Session: Yes Local Node ID: 12244 Local SAP address: 4 Does link support APPN function?: No (Accept other defaults)
APPN config>add link Port name for the link station: TR3270 Station name: STAT002 MAC address of adjacent node:400000003172 Solicit SSCP Session: Yes Local Node ID: 12245 Local SAP address: 8 Does link support APPN function?: No (Accept other defaults) |
6 |
Protocols APPN TN3270E Server General |
TN3270E (checked to enable) IP address : 172.128.1.2 Automatic logoff ( checked to enable) |
APPN config>tn TN3270E config>set Enable TN3270E Server TN3270E Server IP Address: 172.128.1.2 Automatic logoff: Yes (Accept other defaults) | 7 |
Protocols APPN TN3270E Server LUs |
Local PU Name: STAT001 (click on Implicit Pool) LU name mask: @LU1A Number of implicit workstation definitions: 10 Local PU Name: STAT002 (click on Implicit Pool) LU name mask: @LU2A Number of implicit workstation definitions: 10 (click on LUs to define explicit LUs) LU name: PC03A NAU address: 5 (click on Add) |
TN3270E config>add imp Station Name: STAT001 LU name mask: @LU1A Number of Implicit LUs in Pool: 10 TN3270E config>add imp Station Name: STAT002 LU name mask: @LU2A Number of Implicit LUs in Pool: 10 TN3270E config>add lu Station Name: STAT002 LU name: PC03A NAU address: 5 |
8 |
Notes:
|
Figure 13-2. TN3270E Server Config -Highly Scalable, Fault-Tolerant TN3270
View figure.
Table 13-3. TN3270E Server Config -Highly Scalable, Fault-Tolerant TN3270
See page "Highly Scalable, Fault-Tolerant TN3270E" for a description and Figure 13-2 for a diagram of this configuration. This table provides the configuration for the TN A server. See Table 13-4 and Table 13-5 for the configuration of the Network Dispatchers for this example. | |||
Configuration Program Navigation |
Configuration Program Values |
Command-Line Commands |
Notes |
---|---|---|---|
Devices Adapters Slots |
Slot1: 2-Port TR |
See "add dev" on next row |
1 |
Devices Adapters Ports |
Slot 1/Port 1: Interface 0: TR Slot 1/Port 2: Interface 1: TR |
Config>add dev tok (once for each interface) |
2 |
Devices Interfaces |
Interface 0 Mac Address 400022AA0053 Interface 1 Mac Address 400022AA0003 |
Config>net 0 TKR config>set phy 40:00:22:AA:00:53 TKR config>exit Config>net 1 TKR config>set phy 40:00:22:AA:00:03 |
|
System General |
System name: NU_A Location: XYZ Contact: Administrator |
Config>set host Config>set location Config>set contact |
|
System SNMP Config General |
SNMP (checked) |
Config>p snmp SNMP Config>enable snmp |
|
System SNMP Config Communities General |
Community name: admin Access type: Read-write trap Community view: All |
SNMP Config>add community SNMP Config>set comm access write |
3 |
Protocols IP General |
Internal address: 172.128.252.3 Router ID: 172.128.1.3 Same Subnet (checked) |
Config>p ip IP config>set internal 172.128.252.3 IP config>set router-id 172.128.1.3 IP config>enable same-subnet |
4 |
Protocols IP Interfaces |
Interface 0 (TR slot 1 port 1) IP address: 172.128.2.3 Subnet mask: 255.255.255.0
|
IP config>add address 0 172.128.2.3 255.255.255.0 IP config>add address 0 172.128.1.100 255.255.255.0 IP config>add address 1 172.128.1.3 255.255.255.0 |
5,6 |
Protocols IP OSPF General |
OSPF (checked) |
Config>p ospf OSPF Config>enable ospf |
|
Protocols IP OSPF Area Configuration General |
Area number: 0.0.0.0 Stub area (not checked) |
OSPF Config>set area |
|
Protocols IP OSPF Interfaces |
Interface 1 OSPF (checked) |
OSPF Config>set interface Interface IP address: 172.128.1.3 Attaches to area: 0.0.0.0 (Accept other defaults) |
7 |
Protocols APPN General |
APPN network node (checked to enable) Network ID: NUBNODE Control point name: CPNU |
Config>p appn APPN config> set node Enable APPN Network ID: NUBNODE Control point name: CPNU (Accept other defaults) |
8 |
Protocols APPN Interfaces |
(highlight Interface 0 Token Ring) (click on the configure tab) Define APPN port (checked to enable) Port name: TR3270 High performance routing (HPR) supported (unchecked to disable) Support multiple PUs (checked to enable) |
APPN config>add port APPN Port Link Type: TOKEN RING Port name: TR3270 Enable APPN Support multiple PUs High performance routing: No (Accept other defaults) |
9 |
Protocols APPN Interfaces |
(highlight Interface 0 Token Ring) (click on the Link stations tab) STAT001 (new definition) General-1 Tab: Link station name: STAT001 Solicit SSCP session (checked) Link support APPN functions (unchecked) General-2 Tab: MAC address of adjacent node: 400000003172 Node ID: 12244 Local SAP address: 04 (click on Add to create the Link station)
|
APPN config>add link Port name for the link station: TR3270 Station name: STAT001 MAC address of adjacent node: 400000003172 Solicit SSCP Session: Yes Local Node ID: 12244 Local SAP address: 4 Does link support APPN function?: No(Accept other defaults) APPN config>add link Port name for the link station: TR3270 Station name: STAT002 MAC address of adjacent node:400000003172 Solicit SSCP Session: Yes Local Node ID: 12245 Local SAP address: 8 Does link support APPN function?: No (Accept other defaults) |
10 |
Protocols APPN TN3270E Server General |
TN3270E (checked to enable) IP address : 172.128.1.100 Automatic logoff ( checked to enable) |
APPN config>tn TN3270E config>set Enable TN3270E Server TN3270E Server IP Address: 172.128.1.100 Automatic logoff: Yes (Accept other defaults) | 11 |
Protocols APPN TN3270E Server LUs |
Local PU Name: STAT001 (click on Implicit Pool) LU name mask: @LU1A Number of implicit workstation definitions: 10
|
TN3270E config>add imp Station Name: STAT001 LU name mask: @LU1A Number of Implicit LUs in Pool: 10 TN3270E config>add imp Station Name: STAT002 LU name mask: @LU2A Number of Implicit LUs in Pool: 10 |
12 |
Notes:
|
Table 13-4. Network Dispatcher Config -Highly Scalable, Fault-Tolerant TN3270
See page "Highly Scalable, Fault-Tolerant TN3270E" for a description and Figure 13-2 for a diagram of this configuration. This table provides the configuration for the Primary Network Dispatcher, ND A. See Table 13-5 for the configuration of the backup Network Dispatcher. See Table 13-2 for the configuration of the TN3270E servers for this example. | |||
Configuration Program Navigation |
Configuration Program Values |
Command-Line Commands |
Notes |
---|---|---|---|
Devices Adapters Slots |
Slot 1: 2-Port TR |
See "add device" on next row |
1 |
Devices Adapters Ports |
Slot 1/Port 1: Interface 0: TR |
Config>add dev tok |
2 |
Devices Interfaces |
Interface 0 MAC address: 400022AA0001 |
Config>net 0 TKR config>set phy 40:00:22:AA:00:01 |
|
System General |
System name: NU_A Location: XYZ Contact: Administrator |
Config>set host Config>set location Config>set contact |
|
System SNMP Config General |
SNMP (checked) |
Config>p snmp SNMP Config>enable snmp |
|
System SNMP Config Communities General |
Community name: admin Access type: Read-write trap Community view: All |
SNMP Config>add community SNMP Config>set comm access write |
3 |
Protocols IP General |
Internal address: 172.128.252.1 Router ID: 172.128.1.1 |
Config>p ip IP config>set internal 172.128.252.1 IP config>set router-id 172.128.1.1 |
4 |
Protocols IP Interfaces |
Interface 0 (TR slot 1 port 1) IP address: 172.128.1.1 Subnet mask: 255.255.255.0 |
IP config>add address |
|
Protocols IP OSPF General |
OSPF (checked) |
Config>p ospf OSPF Config>enable ospf |
|
Protocols IP OSPF Area Configuration General |
Area number: 0.0.0.0 Stub area (not checked) |
OSPF Config>set area |
|
Protocols IP OSPF Interfaces |
Interface 0 OSPF (checked) |
OSPF Config>set interface Interface IP address 172.128.1.1 Attaches to area 0.0.0.0(Accept other defaults) |
|
Features Network Dispatcher Router Executor |
Executor (checked) |
Config>feat ndr NDR Config>enable executor |
|
Features Network Dispatcher Router Clusters Detail |
Cluster address: 172.128.1.100 |
NDR Config>add cluster Cluster Address: 172.128.1.100 (Accept other defaults) |
|
Features Network Dispatcher Router Clusters Ports |
Port Number 23 |
NDR Config>add port Cluster Address 172.128.1.100 Port number 23 (Accept other defaults) |
|
Features Network Dispatcher Router Clusters Servers |
Server address: 172.128.1.3 172.128.1.4 |
NDR Config>add server Cluster Address: 172.128.1.100 Port number: 23 Server Address: 172.128.1.3 (Accept other defaults) (Repeat for 172.128.1.4) |
|
Features Network Dispatcher Router Manager |
Manager (checked) Proportion Active: 10 New: 10 Advisor: 80 System: 0 |
NDR Config>enable manager NDR Config>set manager propor Active: 10 New: 10 Advisor: 80 System: 0 (Accept other defaults) |
5 |
Features Network Dispatcher Router Advisors |
Advisor (checked) Advisor name: TN3270 Advisor port: 23 Timeout: 10 |
NDR Config>add advisor Advisor name: 3 (for TN3270) Timeout: 10 (Accept other defaults) NDR Config>enable advisor Advisor name: 3 (for TN3270) Port number: 23 |
6 |
Features Network Dispatcher Router Backup |
Backup (checked to enable) Backup role: PRIMARY Switch back Strategy: MANUAL |
NDR Config>add backup Role: 0=PRIMARY Switch back strategy: 1=MANUAL |
7 |
Features Network Dispatcher Router Reaches |
Reach address: (Enter each address and click on Add) 172.128.1.3 172.128.1.4 |
NDR Config>add reach Address to reach: 172.128.1.3 (Repeat for 172.128.1.4) |
8 |
Features Network Dispatcher Router Heart Beats |
Source address: 172.128.1.1 Target address: 172.128.1.2 (Enter addresses and click on Add) |
NDR Config>add heartbeat Source Heartbeat address: 172.128.1.1 Target Heartbeat Address: 172.128.1.2 |
8 |
Notes:
|
Table 13-5. Network Dispatcher Config -Highly Scalable, Fault-Tolerant TN3270
See page "Highly Scalable, Fault-Tolerant TN3270E" for a description and Figure 13-2 for a diagram of this configuration. This table provides the configuration differences for the backup Network Dispatcher ND B based on Table 13-4, which gives the configuration for the primary Network Dispatcher. The definition for the backup Network Dispatcher is the same as for the Primary except for the differences that are shown in this table. These differences correspond to the interface addresses and the Network Dispatcher backup functions. The parameters related to the Network Dispatcher that are not shown here must be identical to the values configured on the primary. It is also recommended that the hardware configuration be the same for both the primary and backup Network Dispatchers. See Table 13-3 for the configuration of the TN3270E servers for this example. | |||
Configuration Program Navigation |
Configuration Program Values |
Command-Line Commands |
Notes |
---|---|---|---|
Devices Interfaces |
Interface 0 MAC Address 400022AA0002 |
Config>net 0 TKR config>set phy 40:00:22:AA:00:02 |
|
System General |
System name: NU_ND2 |
Config>set host |
|
Protocols IP General |
Internal address: 172.128.252.2 Router ID: 172.128.1.2 |
Config>p ip IP config> set internal 172.128.252.2 set router-id 172.128.1.2 |
1 |
Protocols IP Interfaces |
Interface 0 (TR slot 1 port 1) IP address: 172.128.1.2 Subnet mask: 255.255.255.0 |
Config>p ip IP config>add address |
|
Protocols IP OSPF Interfaces |
Interface 0 OSPF (checked) |
Config>p ospf OSPF Config>set interface Interface IP address: 172.128.1.2 Attaches to area: 0.0.0.0 (accept other defaults) |
|
Features Network Dispatcher Router Backup |
Backup (checked to enable) Backup role: BACKUP Switch back Strategy: MANUAL |
Config>feat NDR NDR Config>add backup Role: 1=BACKUP Switch back strategy: 1=MANUAL |
|
Features Network Dispatcher Router Heart Beats |
Source address: 172.128.1.2 Target address: 172.128.1.1 (Enter addresses and click on Add) |
NDR Config>add heartbeat Source Heartbeat address: 172.128.1.2 Target Heartbeat Address: 172.128.1.1 |
2 |
Notes:
|
Figure 13-3. TN3270 via DLUR over APPN
View figure.
Table 13-6. TN3270 via DLUR over APPN
See page "TN3270 Via DLUR over APPN" for a description and Figure 13-3 for a diagram of this configuration. | |||
Configuration Program Navigation |
Configuration Program Values |
Command-Line Commands |
Notes |
---|---|---|---|
Devices Adapters Slots |
Slot1: 2-Port TR |
See "add dev" on next row |
1 |
Devices Adapters Ports |
Slot 1/Port 1: Interface 0: TR |
Config>add dev tok |
2 |
Devices Interfaces |
Interface 0 Mac Address 400022AA0011 |
Config>net 0 TKR config>set phy 40:00:22:AA:00:11 |
|
System General |
System name: NU_A Location: XYZ Contact: Administrator |
Config>set host Config>set location Config>set contact |
|
System SNMP Config General |
SNMP (checked) |
Config>p snmp SNMP Config>enable snmp |
|
System SNMP Config Communities General |
Community name: admin Access type: Read-write trap Community view: All |
SNMP Config>add community SNMP Config>set comm access write |
3 |
Protocols IP General |
Internal address: 172.128.252.2 Router ID: 172.128.1.2 |
Config>p ip IP config>set internal 172.128.252.2 IP config>set router-id 172.128.1.2 |
|
Protocols IP Interfaces |
Interface 0 (TR slot 1 port 1) IP address: 172.128.1.2 Subnet mask: 255.255.255.0 |
IP config>add address |
|
Protocols IP OSPF General |
OSPF (checked) |
Config>p ospf OSPF Config>enable ospf |
|
Protocols IP OSPF Area Configuration General |
Area number: 0.0.0.0 Stub area (not checked) |
OSPF Config>set area |
|
Protocols IP OSPF Interfaces |
Interface 0 OSPF (checked) |
OSPF Config>set interface Interface IP address: 172.128.1.2 Attaches to area: 0.0.0.0 (Accept other defaults) |
|
Protocols APPN General |
APPN network node (checked to enable) Network ID: STFNET Control point name: NUTN |
Config>p appn APPN config> set node Enable APPN Network ID: STFNET Control point name: NUTN (Accept other defaults) |
|
Protocols APPN Interfaces |
(highlight Interface 0 Token Ring) (click on the configure tab) Define APPN port (checked to enable) Port name: TR001 |
APPN config>add port APPN Port Link Type: TOKEN RING Port name: TR001 Enable APPN (Accept other defaults) |
4 |
Protocols APPN Interfaces |
(highlight Interface 0 Token Ring) (click on the Link stations tab) TRTG001 (new definition) General-1 Tab: Link station name: TRTG001 General-2 Tab: MAC address of adjacent node: 400022AA0001 Adjacent Node Type: APPN Network Node (click on Add to create the Link station) |
APPN config>add link Port name for the link station: TR001 Station name: TRTG001 MAC address of adjacent node: 400022AA0001 (Accept other defaults) |
5 |
Protocols APPN DLUR |
DLUR (checked to enable) Fully-qualified CP name of primary DLUS: STFNET.MVS1 |
APPN config>set dlur Enable DLUR Fully-qualified CP name of primary DLUS: STFNET.MVS1 (Accept other defaults) |
6 |
Protocols APPN TN3270E Server General |
TN3270E (checked to enable) IP address : 172.128.1.2 Automatic logoff ( checked to enable) |
APPN config>tn TN3270E config>set Enable TN3270E Server TN3270E Server IP Address: 172.128.1.2 Automatic logoff: Yes (Accept other defaults) | 7 |
Protocols APPN TN3270E Server Local PUs |
Link Station Name: PUPS08T Node ID: 12244
|
TN3270E config>exit APPN config>add loc Station Name: PUPS08T Local Node ID: 12244 (Accept other defaults)
APPN config>add loc Station Name: PUPS18T Local Node ID: 12245 (Accept other defaults) |
8 |
Protocols APPN TN3270E Server LUs |
Local PU Name: PUPS08T (click on Implicit Pool) LU name mask: @LU1A Number of implicit workstation definitions: 5 Local PU Name: PUPS18T (click on Implicit Pool) LU name mask: @LU2A Number of implicit workstation definitions: 5 |
APPN config>tn TN3270E config>add imp Station Name: PUPS08T LU name mask: @LU1A Number of Implicit LUs in Pool: 5 TN3270E config>add imp Station Name: PUPS18T LU name mask: @LU2A Number of Implicit LUs in Pool: 5 |
9 |
Notes:
|
This scenario was done with an MVS running VTAM V4R4 and an IBM 2216 which was ESCON attached to the host. The Network Utility had a two-port token-ring adapter in slot 1 and an ESCON adapter in slot 2. LSA loopback protocol was used for communication over the ESCON channel. The Network Utility was defined as a Network Node, and it used APPN/ISR to communicate with VTAM. The TN3270E PUs and LUs were connected to VTAM using DLUR/DLUS.
The DDDLU function was tested using the following VTAM definitions:
The 2216 configuration file for this scenario was DDD.
Figure 13-4 shows the relationships of different parameters in both VTAM and the 2216 for this scenario.
View figure. |
Table 13-7 lists the actual VTAM XCA major node used.
Table 13-7. XCA Major Node X5303 for ESCON channel connection
**************************Top of Data *********************** X5303 VBUILD TYPE=XCA X5303 VBUILD TYPE=XCA X5303PRT PORT ADAPNO=0, X5303PRT PORT ADAPNO=0, * CUADDR=284, * SAPADDR=4, * MEDIUM=RING X5303GRP GROUP DIAL=YES,CALL=INOUT,DYNPU=YES, * AUTOGEN=(1,L,P) *********************** Bottom of Data ******************* |
Table 13-8 contains the actual VTAM SW5303N switched major node for the Network Node in 2216.
Table 13-8. Switched Major Node SW5303N for 2216 Network Node
***************************** Top of Data ****************************** SW5303N VBUILD TYPE=SWNET P2216N PU ADDR=02, X PUTYPE=2, X CPCP=YES, X CONNTYPE=APPN, X USSTAB=US327X, X NN=YES, X DYNLU=YES, X CPNAME=NN2216 **************************** Bottom of Data **************************** |
For APPN Control Point PUs, such as the Network Node shown in Table 13-8, you do not need ID Block nor ID NUm numbers. Network Nodes can recognize each other by fully qualified network names.
Table 13-9. LUGROUP Major Node DDGROUP, Model for LU Definitions
***************************** Top of Data ****************************** DDGROUP VBUILD TYPE=LUGROUP GROUP1 LUGROUP 3270@ LU DLOGMOD=D4C32XX3,LOGAPPL=RA03T 1 **************************** Bottom of Data **************************** |
Table 13-10. Switched Major Node DDDPU for the Dynamically Defined LUs
***************************** Top of Data ****************************** DDDPU VBUILD TYPE=SWNET DDPU PU ADDR=02, X IDBLK=077, 1 X IDNUM=22160, X PUTYPE=2, X USSTAB=US327X, X LUGROUP=GROUP1, 2 X LUSEED=DDLU###, 3 X DLOGMOD=D4C32XX3 **************************** Bottom of Data **************************** |
Table 13-11. DDD Configuration Done With MAS 3.3 Configuration Program (Part 1 of 2)
Configuration Program Navigation | Configuration Program Values |
---|---|
Devices Slots |
Slot 1: 2-Port TR Slot 2: ESCON |
Devices Channel Adapters ESCON Interfaces ESCON Interfaces |
Protocol Type: LSA LAN Type: Token Ring MAC Address (for LSA virtual LAN, VTAM side): e.g. 40002216000A Click on Loopback Click on Add |
Devices Channel Adapters ESCON Interfaces ESCON Subchannels |
Device Addresses: 4 Subchannel type: read/write LPAR: 1 Link address: CC CU: 1 Click on Add |
Devices Channel Adapters APPN Loopback Net |
LAN type: Token Ring MAC Address: 40002216000B Click on Add |
System General |
System name: DDD Location: Machine room Contact: your name |
System Users |
Name: userid Permission: Administrative Password: password Repeat password: password Click on Add |
System SNMP Config Communities General |
Name: public Access type: Read-write trap Click on Add |
Protocols IP Details |
Internal address: 9.24.104.203 |
Protocols IP Interfaces |
Interface 1 (TR slot 1 port 2) IP address: 9.24.106.9 Subnet mask: 255.255.255.0 Click on Add IP address: 9.24.104.203 Subnet mask: 255.255.255.0 Click on Add |
Protocols APPN General |
Click on APPN network node Network ID: USIBMRA Control point name: NN2216 |
Protocols APPN DLUR |
Click on DLUR Fully qualified name of primary DLUS: USIBMRA.RA03M |
Table 13-12. DDD Configuration, Done With MAS 3.3 Configuration Program (Part 2 of 2)
Configuration Program Navigation | Configuration Program Values |
---|---|
Protocols APPN Interfaces |
Click on the line item APPN Net--Token Ring Click on heading Configure (Tab General selected) Click on Define APPN Port Click on Service Any Node Click off High Performance Routing (HPR) Supported Click on Support Multiple PUs Select tab Port Definition Specify Local SAP address: 04 |
Protocols TN3270E Server General |
Click on TN3270E IP address: 9.24.104.203 |
Protocols TN3270E Server Local PUs |
Link station name: TNDDD1 Node ID: 22160 Primary DLUS: USIBMRA.RA03M Click on Add |
Protocols TN3270E Server LUs |
Select TNDDD1 Click on heading LUs LU name: DDLU2 Class: Implicit NAU address: 2 Click on Add Repeat LU name, Class, NAU address Add sequence for each LU |
In Network Utility, you can monitor the status of connections in use, pools, mappings and more, generally under talk 5/appn/tn3270e.
To get a list of all locally defined resources such as LUs, PUs and pools, you can use talk 6/appn/tn3270e. See Table 13-13 for the TN3270E configuration.
Table 13-13. Listing of TN3270E Configuration Under talk 6/p app/tn3270e
DDD TN3270E config>LIST ALL TN3270E Server Definitions TN3270E enabled: YES TN3270E IP Address: 9.24.104.203 TN3270E Port Number: 23 Default Pool Name : PUBLIC NetDisp Advisor Port Number: 10008 Client IP Address Mapping : N Keepalive type: NONE Automatic Logoff: N Timeout: 30 Enable IP Precedence: N DLUS Link Station: TNDDD1 Fully-qualified CP name of primary DLUS: USIBMRA.RA03M Fully-qualified CP name of backup DLUS: Local Node ID: 22160 Auto activate : YES Host Initiated Dynamic LU Definition : NO LU Name NAU addr Class Assoc LU Name Assoc NAU addr ----------------------------------------------------------------------- DDLU2 2 Implicit Workstation DDLU3 3 Implicit Workstation DDLU4 4 Implicit Workstation --More-- DDLU5 5 Implicit Workstation DDLU6 6 Explicit Workstation DDLU7 7 Explicit Workstation Client IP Address mapping -------------------------- Client IP Address Address Mask Resource Name ------------------------------------------------------ Multiple Port ------------------------------ Port Number Enable TN3270E Resource Name ------------------------------------------------- DDD TN3270E config> |
The commands in Table 13-14 take you first to talk 5/appn/tn3270e.
The list status then displays the current status of TN3270E resources. There are no end user sessions active at this time, but a PU with 6 LUs is active in SSCP-LU session.
Table 13-14. Moving to talk 5/appn/tn3270 for TN3270E Status
DDD *TALK 5 DDD +PROTOCOL APPN APPN GWCON DDD APPN >TN3270E TN3270E GWCON DDD TN3270E >LIST STATUS TN3270E Server Status Summary TN3270E IP Address: 9.24.104.203 NetDisp Advisor Port Number: 10008 Keepalive type: None Automatic Logoff: N Client IP Address mapping : N Number of connections : 1 Number of available LUA LU's : 5 Number of LUA LU's pending termination : 0 Number of defined LU's : 6 Number of connections in SSCP-LU state : 0 Number of connections in LU-LU state : 1 1 DDD TN3270E > |
This number increases with the LU-LU sessions established between LUs defined under Network Utilities and VTAM applications.
After the first user has established a session and left the LU name field blank in the client, LIST CONNECTIONS under talk 5/appn/tn3270e looks like Table 13-15:
Table 13-15. First Session Established, LU Selected From Default Pool
DDD TN3270E >LIST CONNECTIONS Connection information for all the LUs Local LU Class Assoc LU Client Addr Status Prim LU Sec LU Idle Min ------------------------------------------------------------------------------ DDLU5 IW 9.24.106.217 LU-LU RA03T07 DDLU005 0 DDD TN3270E > |
After a second user gets his session, again with no specific LU or pool name, the list of connections looks like Table 13-16:
Table 13-16. Two Sessions Using the Default Pool
DDD TN3270E >LIST CONNECTIONS Connection information for all the LUs Local LU Class Assoc LU Client Addr Status Prim LU Sec LU Idle Min ------------------------------------------------------------------------------ DDLU2 IW 9.24.106.127 LU-LU RA03T08 DDLU002 0 DDLU5 IW 9.24.106.217 LU-LU RA03T07 DDLU005 4 DDD TN3270E > |
Table 13-17 is an example of how the list of connections looks when a third user, requesting explicit LU DDLU7, gets connected.
Table 13-17. List of Connections With Two Implicit and One Explicit LU User
DDD TN3270E >LIST CONNECTIONS Connection information for all the LUs Local LU Class Assoc LU Client Addr Status Prim LU Sec LU Idle Min ------------------------------------------------------------------------------ DDLU7 EW 9.24.106.146 LU-LU RA03T09 DDLU007 0 DDLU2 IW 9.24.106.127 LU-LU RA03T08 DDLU002 6 DDLU5 IW 9.24.106.217 LU-LU RA03T07 DDLU005 6 DDD TN3270E > |
This scenario was established with an MVS running VTAM V4R4 and an IBM Network Utility, which was ESCON attached to the host. In the Network Utility, there was a two-port token-ring adapter in slot 1 and an ESCON adapter in slot 3. LSA loopback protocol was used for communication over the ESCON channel. The Network Utility was defined as a Network Node and it used APPN/ISR to communicate with VTAM. The TN3270E PUs and LUs were connected to VTAM using DLUR/DLUS.
The Host Initiated Dynamic LU (HIDLU) Definition function was tested using the following VTAM definitions:
Note: | To VTAM, all LUs--implicit or explicit--are defined the same. An LU becomes explicit or implicit based on pool definitions in the Network Utility. |
The parameter relationships between VTAM and Network Utility configuration are shown in Figure 13-5.
Figure 13-5. Relationship of Parameters for HIDLU Definition Configuration
View figure. |
The actual SWHID switched major node is shown in Table 13-18.
Table 13-18. Switched Major Node SWHID1 Definition in VTAM
***************************** Top of Data ****************************** SWHID1 VBUILD TYPE=SWNET TNHID1 PU ADDR=02, X IDBLK=077, 1 X IDNUM=22161, X PUTYPE=2, X USSTAB=US327X, X INCLUD0E=YES, 2 X DLOGMOD=D4C32XX3 LU2 LU LOCADDR=02,LOGAPPL=RA03T LU3 LU LOCADDR=03,LOGAPPL=RA03T LU4 LU LOCADDR=04,LOGAPPL=RA03T LU5 LU LOCADDR=05,LOGAPPL=RA03T **************************** Bottom of Data **************************** |
These LUs will become defined in Network Utility with the names shown here (LU2 through LU5). Since the LUs representing these VTAM network NAUs are not already defined to the TN3270E server, the LUs will become explicit LUs.
For a TN3270 client, to get one of these LUs, the LU name must be defined in the client's LU name field.
You can also define Host Initiated Dynamic LUs to go to a pool in Network Utility. This is done in the MAS configuration program (or talk 6) by defining one or more pools in the Network Utility and specifying number of LUs or LU ranges, as well as an LU name mask for the LUs going into a pool. The following LUs under PU TNIMP1 were defined this way.
Table 13-19. Switched Major Node SWIMP1 Definition in VTAM
***************************** Top of Data ****************************** SWIMP1 VBUILD TYPE=SWNET TNIMP1 PU ADDR=02, X IDBLK=077, 1 X IDNUM=22165, X PUTYPE=2, X USSTAB=US327X, X INCLUD0E=YES, 2 X DLOGMOD=D4C32XX3 IMPLU2 LU LOCADDR=02,LOGAPPL=RA03T IMPLU3 LU LOCADDR=03,LOGAPPL=RA03T IMPLU4 LU LOCADDR=04,LOGAPPL=RA03T IMPLU5 LU LOCADDR=05,LOGAPPL=RA03T IMPLU6 LU LOCADDR=06,LOGAPPL=RA03T **************************** Bottom of Data **************************** |
LUs defined in switched major node SWIMP will become both implicit and explicit LUs in the Network Utility due to definitions in MAS configuration, as shown in Table 13-21.
The first three LUs--IMPLU2, IMPLU3 and IMPLU4--go to pool HIDP. A TN3270E user can get one of these LUs by leaving the LU name field empty in the TN3270E client.
The next LU, IMPLU5, has been defined in the MAS configuration program to go into the default pool, <DEFLT>. A user can get this LU by leaving the LU name field empty in the TN3270E client.
For the last LU, IMPLU6, no pool has been defined in the Network Utility. It becomes thus an explicit LU, named IMPLU6.
Note: | When you define a pool in TN3270E server, you must also give an LU name mask. This mask actually overrides the LU name of VTAM, and the implicit LUs that belong to a pool will have names based on the LU name mask. Only when you define explicit LUs (which do not go to a pool), do you get the LU names directly from VTAM. |
Table 13-20. HIDLU Configuration, Done With MAS 3.3 Configuration Program (Part 1 of 2)
Configuration Program Navigation | Configuration Program Values |
---|---|
Devices Slots |
Slot 1: 2-Port TR Slot 2: ESCON |
Devices Channel Adapters ESCON Interfaces ESCON Interfaces |
Protocol Type: LSA LAN Type: token ring MAC Address: (for LSA virtual LAN, VTAM side): e.g. 40002216000A Click on Loopback Click on Add |
Devices Channel Adapters ESCON Interfaces ESCON Subchannels |
Device address: 4 Subchannel type: read/write LPAR: 1 Link address: CC CU: 1 Click on Add |
Devices Channel Adapters APPN Loopback Net |
LAN type: token ring MAC address: 40002216000B Click on Add |
System General |
System name: HID Location: Machine room Contact: your name |
System Users |
Name: userid Permission: Administrative Password: password Repeat password: password Click on Add |
System SNMP Config Communities General |
Name: public Acess type: Read-write trap Click on Add |
Protocols IP Details |
Internal address: 9.24.104.203 |
Protocols IP Interfaces |
Interface 1 (TR slot 1 port 2) IP address: 9.24.106.9 Subnet mask: 255.255.255.0 Click on Add IP address: 9.24.104.203 Subnet mask: 255.255.255.0 Click on Add |
Protocols APPN General |
Click on APPN network node Network ID: USIBMRA Control point name: NN2216 |
Protocols APPN DLUR |
Click on DLUR Fully qualified name of primary DLUS: USIBMRA.RA03M |
Table 13-21. HIDLU Configuration, Done With MAS 3.3 Configuration Program (Part 2 of 2)
Configuration Program Navigation | Configuration Program Values |
---|---|
Protocols APPN Interfaces |
Click on line item APPN Net--token ring Click on heading Configure (Tab General selected) Click on Define APPN Port Click on Service Any Node Click off High Performance Routing (HPR) Supported Click on Support Multiple PUs Select tab Port Definition Specify Local SAP address: 04 |
Protocols TN3270E Server General |
Click on TN3270E IP address: 9.24.104.203 |
Protocols TN3270E Server Pools |
Pool name: HIDP Click on Add |
Protocols TN3270E Server Local PUs |
Link station name: HIDPU1 Node ID: 22161 Click on Host-Initiated Dynamic LUs allowed for PU Primary DLUS: USIMBRA.RA03M Click on Add Link station name: HIDPU2 Click on Host-Initiated Dynamic LUs allowed for PU Node ID: 22165 Primary DLUS: USIBMRA.RA03M Click on Add |
Protocols TN3270E Server LUs |
Select line HIDPU2 Click on heading Implicit pools Select pool name: <DEFLT> LU name mask: IMPLU Click on Specify Address Ranges Address Ranges: 5 Click on Add Select Pool name: HIDP LU name mask: LUIMP Click on Specify Address Ranges Address Ranges: 2-4 Click on Add |
The HIDLU configuration can be monitored in talk 5 under protocol appn and tn3270e.
Under talk 5, you can monitor all the interfaces as shown in Table 13-22:
Table 13-22. Listing Interfaces Command Under Talk 5
HID +INTERFACE Self-Test Self-Test Maintenance Net Net' Interface Slot-Port Passed Failed Failed 0 0 TKR/0 Slot: 1 Port: 1 1 0 0 1 1 TKR/1 Slot: 1 Port: 2 1 0 0 2 2 ESCON/0 Slot: 3 Port: 1 1 0 0 3 2 LSA/0 Slot: 0 Port: 0 1 3 0 4 4 TKR/2 Slot: 0 Port: 0 1 0 0 |
Table 13-23. Statistics Under Talk 5
HID +STATISTICS Net Interface Unicast Multicast Bytes Packets Bytes Pkts Rcv Pkts Rcv Received Trans Trans 0 TKR/0 22521 25742 1399673 22522 472997 1 TKR/1 24301 1476136 97150812 23588 582533 2 ESCON/0 11453 0 2976076 9930 1481020 3 LSA/0 11452 0 2976060 9929 1480999 4 TKR/2 0 0 0 0 0 |
By issuing command p app ( protocol appn) at talk 5 level, you can monitor APPN-related functions, such as verifying CP-CP connections as in Table 13-24.
Table 13-24. Verifying NN-NN Connection To VTAM
HID +PROTOCOL APPN HID APPN >LIST CP-CP_SESSIONS CP Name Type Status ConWinner ConLoser ConWinner ConLoser ID ID Sense Sense =========================================================================== USIBMRA.RA03M NN Active 3710C590 3710C592 00000000 00000000 |
TN3270E functions are under APPN and can be reached by issuing the command,
TN3270E, as in Table 13-26. At TN3270E level, you can only issue
LIST command with the completions in Table 13-25:
Table 13-25. LIST Options Under TN3270E
HID TN3270E >LIST ? Possible completions: CONNECTIONS MAPPING POOLS PORTS STATUS (you may cycle through these commands by pressing the TAB key) HID TN3270E >LIST |
Table 13-26. Monitoring TN3270E Sessions
HID APPN >TN3270E TN3270E GWCON HID TN3270E >LIST CONNECTIONS Connection information for all the LUs Local LU Class Assoc LU Client Addr Status Prim LU Sec LU Idle Min ------------------------------------------------------------------------------ IMPLU5 IW 9.24.106.127 LU-LU RA03T01 IMPLU5 38 |
Table 13-26 shows the TN3270E connections after the first session was established. The TN3270E client had defined no LU name, so an LU from the default pool was selected.
Another user then makes a TN3270E connection, specifying HIDP pool name as
the LU name in the client. Table 13-27 is an example of what the list looks like:
Table 13-27. LIST CONNECTIONS After Second User In Session
HID TN3270E >LIST CONNECTIONS Connection information for all the LUs Local LU Class Assoc LU Client Addr Status Prim LU Sec LU Idle Min ------------------------------------------------------------------------------ LUIMP4 IW 9.24.106.217 LU-LU RA03T07 IMPLU4 1 IMPLU5 IW 9.24.106.127 LU-LU RA03T01 IMPLU5 45 |
If a third user establishes a session, defining IMPLU6 in the client, the list of connections looks like the one in Table 13-28:
Table 13-28. LIST CONNECTIONS After Third User Has Connected
HID TN3270E >LIST CONNECTIONS Connection information for all the LUs Local LU Class Assoc LU Client Addr Status Prim LU Sec LU Idle Min ------------------------------------------------------------------------------ IMPLU6 EW 9.24.106.146 LU-LU RA03T09 IMPLU6 0 LUIMP4 IW 9.24.106.217 LU-LU RA03T07 IMPLU4 4 IMPLU5 IW 9.24.106.127 LU-LU RA03T01 IMPLU5 48 |
For the HOD Client Cache function, you should configure both the TN3270E server and HOD function under Network Dispatcher. For this configuration, you can keep exactly the same configuration as for the TN3270E server, which is done in Table 13-11 for DDDLU and Table 13-20 for HIDLU. In this scenario, HIDLU definitions were used for TN3270E server.
For the HOD Client Cache part of the environment, Network Dispatcher 'Executor' and HOD Client Cache should both be defined, in addition to the other definitions already done in HIDLU or DDDLU (in previous sections in this chapter).
For the HOD Server installation in this scenario, the following products were installed: NT Server, NT Service Pack 3, Web Server, and HOD Server.
The Loopback address on the HOD Server box should be defined to point to the Network Dispatcher Cluster IP address. The Network Dispatcher Cluster IP address can not be pinged.
In the following scenario, the Loopback adapter was defined on MS NT Server in the following way:
When defining the HOD Server, do not forget to take the following action as well. In the scenario for the Windows NT Server, the cluster IP address (9.24.104.207) is found in the gateway column after issuing the command netstat -r. In this column, you should delete the extraneous routes if you see more than one entry with the Cluster IP address. Delete the one starting with the same network address as Cluster IP address and with the rest being zeros. In this case, the entry to be deleted is the line with IP address 9.0.0.0 .
Figure 13-6. HOD Client Cache Parameter Relationships
View figure. |
For the Host On-Demand Client Cache configuration, the HOD is only added on top of the DDDLU or HIDLU configuration as done previously in Table 13-11 or Table 13-20, since these already contain TN3270E configurations.
Table 13-29. HOD Client Cache Configuration
Configuration Program Navigation | Configuration Program Values | |||
---|---|---|---|---|
Devices Interfaces |
Interface 0: Slot/Port=1/1 Click Interface | |||
Protocols IP Interfaces Addresses |
Click on Interface 0 IP address: 192.168.141.82 Mask 255.255.255.240 in our scenario Click on ADD | |||
Protocols IP OSPF Interfaces |
Click on address 192.168.141.82 Check OSPF box | |||
Features Network Dispatcher Executor |
Click Executor (executor 'on') | |||
Features Network Dispatcher Clusters Details |
Cluster address: 9.24.104.207 The rest is default values. Click on ADD | |||
Features Network Dispatcher Clusters Ports |
Number 80 8989 8999 |
Type Both Both Both |
Mode HOD Client None None |
Weight 20 20 20 |
Features Network Dispatcher Clusters Servers |
For all three ports: Address: 192.168.141.81 (NT Server) Weight: 20 Server state: up Click ADD | |||
Features Network Dispatcher Clusters HOD Client Cache Proxies |
Default values excepted | |||
Features Network Dispatcher Clusters HOD Client Cache Partitions |
Partitions: Default applet: *.jar The other parameters left to default URL mask: URL mask: *jre URL mask type: Include Click on ADD |
In this example, Netscape browser was pointed to http://9.24.104.207/hod/hod.html and the screen seen in Figure 13-7 came up. Right mouse-click on the 3270 icon to get the screen seen in Figure 13-8. In Figure 13-8, the TN3270E server parameters are defined the same as in the Network Utility.
Figure 13-7. HOD Client Screen On Internet Browser (Netscape)
View figure. |
Figure 13-8. TN3270E Server Definition on HOD Client
View figure. |
After this definition, if you double-click (with left mouse button) on the 3270 icon, the following screen (Figure 13-9) comes up.
Figure 13-9. HOD Client Screen After Connection Established
View figure. |
The following commands are issued in order to monitor the HOD
configuration.
Table 13-30. Start of Monitoring Cache in T5/ELS
HODCAC0 *TALK 5 HODCAC0 +EVENT HODCAC0 ELS>NODISPLAY SUBSYSTEM ALL ALL Complete HODCAC0 ELS>DISPLAY SUBSYSTEM WEBH ALL HODCAC0 ELS> ..(Ctrl-P) HODCAC0 *TALK 2 : 00:00:01 DOLOG: Server 192.168.141.81 has been set up. : 00:20:01 WEBH.017: Client connection 31AE11C accepted as Socket 31BF564 00:20:01 WEBH.015: Conn (31AE11C) HTTP Proxy(cluster 9.24.104.207 port 80) partition (0) opened 00:20:01 WEBH.009: HTTP Proxy(cluster 9.24.104.207 port 80) conn (31AE11C) new req being parsed 00:20:01 WEBH.012: HTTP Proxy(cluster 9.24.104.207 port 80) partition (0) conn (31AE11C) not using cache because object not found in cache 1 : : : |
Table 13-31. Monitoring HOD Client Cache Definition
HODAC0 +FEATURE Feature name or number [WAN Restoral System] ? hod Host On-Demand Client Cache Console HODCAC0 HOD Client Cache>LIst All HOD Client Cache Partition 0 Status: Enabled Cluster address: 9.24.104.207 Port 80 1 partition(s) active. External Cache Manager: Disabled |
Table 13-32. Listing HOD Client Cache
HODCAC0 HOD Client Cache>LIst PArtition HOD Client Cache Partition 0 Status: Enabled Cluster address: 9.24.104.207 Port 80 Partition size: Current - 1030296 bytes Highest - 1030296 bytes Maximum - Unlimited Number of objects: Current - 37 Highest - 37 Maximum - Unlimited Maximum object size: Unlimited HOD Client Cache purge interval : 600 minute(s) Hit ratio: 61% Total number of hits: 59 1 Total number of misses: 37 Object Excluded (Object too large): 0 (Object expired) 0 (DONT CACHE header): 0 (URL Mask excluded): 0 (Image excluded): 0 (Static object excluded): 0 (Dynamic object excluded): 0 (Cache disabled): 0 Objects explicitly Included: 0 Total number of purged objects: 0 Purged objects (Cache full): 0 (Object stale): 0 (Purged by user): 0 (Invalidation): 0 |
Table 13-33. Displaying the Screen When Another HOD Client Requests Java Applets
HODCAC0 HOD Client Cache>LIst PArtition HOD Client Cache Partition 0 Status: Enabled Cluster address: 9.24.104.207 Port 80 Partition size: Current - 1030296 bytes Highest - 1030296 bytes Maximum - Unlimited Number of objects: Current - 37 Highest - 37 Maximum - Unlimited Maximum object size: Unlimited HOD Client Cache purge interval : 600 minute(s) Hit ratio: 61% 1 Total number of hits: 59 2 Total number of misses: 37 Object Excluded (Object too large): 0 (Object expired) 0 ..... : : |
Now, the TN3270E connections can be monitored in the same way as in DDDLU and HIDLU sections earlier in this chapter.
For the TN3270E Subarea SNA over DLSw function scenario, see Figure 13-10. Network Utility A is ESCON channel attached and also
connected to Network Utility B over a PPP link. As seen in the
configuration screens below, there is no APPN function on Network Utility A
since the connection to VTAM-Host is Subarea. On the host, a VTAM
Switched Major Node (with IDNUM parameter) pointing to the Local Node-ID in
Network Utility (which is '221B1' in our sample scenario) needs to
be defined. Although this is a pure Subarea SNA connection, the
definition is done under APPN on Network Utility B.
Table 13-34. DLSw Configuration on Network Utility A
dlsa-ok DLSw config>ENABLE DLSW Data Link Switching is now enabled dlsa-ok DLSw config>ADD TCP Enter the DLSw neighbor IP Address [0.0.0.0]? 172.16.220.253 Connectivity Setup Type (a/p) [a]? p Transmit Buffer Size (Decimal) [5120]? Receive Buffer Size (Decimal) [5120]? Maximum Segment Size (Decimal) [1024]? TCP Keepalive (E/D) [D]? NetBIOS SessionAlive Spoofing (E/D) [D]? Neighbor Priority (H/M/L) [M]? TCP Neighbor has been changed dlsa-ok DLSw config>OPEN-SAP Enter Interface number [0]? 1 Enter the SAP in hex (range 0-FE), 'SNA', 'NB', or 'LNM' [4]? sna |
This is the definition needed for Network Utility A as seen in Table 13-34 above andFigure 13-10.
When Network Utility B is configured, DLSw and TN3270E Server under the
APPN prompt need to be configured.
Table 13-35. DLSw Configuration on Network Utility B
dlsb-ok DLSw config>ENABLE DLSW Data Link Switching is now enabled dlsb-ok DLSw config>ADD TCP Enter the DLSw neighbor IP Address [0.0.0.0]? 9.24.104.203 Record already exists, can be changed Connectivity Setup Type (a/p) [a]? a Transmit Buffer Size (Decimal) [5120]? Receive Buffer Size (Decimal) [5120]? Maximum Segment Size (Decimal) [1024]? TCP Keepalive (E/D) [D]? NetBIOS SessionAlive Spoofing (E/D) [D]? Neighbor Priority (H/M/L) [M]? TCP Neighbor has been changed dlsb-ok DLSW config>OPEN-SAP Enter Interface number [0]? 1 Enter SAP in hex (range 0-FE), 'SNA', 'NB', or 'LNM' [4]? sna dlsb-ok DLSw config>EXIT |
Table 13-36. Loading APPN and TN3270E Packages If Not Already Loaded
2216 Config>load add package appn appn package configured successfully This change requires a reload. 2216 Config>load add package tn3270e tn3270e package configured successfully This change requires a reload. |
If the APPN and/or TN3270E packages are not loaded, they must be loaded from the operational code to the memory in order for you to work with them. To load APPN and TN3270E packages, see Table 13-36 above.
Table 13-37. Adding Link Station under APPN
dlsb-ok Config>PROTOCOL APPN dlsb-ok APPN config>ADD/UPDATE LINK-STATION APPN Station Port name for the link station [ ]? dls65 Station name (Max 8 characters) [ ]? tnpub1 WARNING!! You are changing an existing record. Activate link automatically (Y)es (N)o [Y] MAC address of adjacent node [40002216000A]? SAP address of adjacent node (04-EC) [4]? Solicit SSCP Session: (Y)es (N)o [Y]? Local Node ID (5 hex digits) [221B1]? Enable Host Initiated Dynamic LU Definition : (Y)es (N)o [N]? Local SAP address (04-EC) [4]? Does link support APPN function: (Y)es (N)o [N]? N Edit TG Characteristics: (Y)es (N)o [N}? Write this record? [Y]? y The record has been written. |
Table 13-38. Adding Port Under APPN
dlsb-ok APPN config>ADD/UPDATE PORT APPN Port Link Type: (P)PP, (FR)AME RELAY, (E)THERNET, (T)OKEN RING, (M)PC, (S)DLC, (X)25, (FD)DI, (D)LSw, (A)TM, (I)P, [ ]? d Port Name (Max 8 characters) [D65534]? dls65 WARNING!! You are changing an existing record. Enable APPN on this port (Y)es (N)o? y Port Definition Support multiple PU (Y)es (N)o [Y] y All active port names will be of the form <port name sap> Service any node: (Y)es (N)o [N] n Maximum BTU size (768-4096) [2048]? Maximum number of link stations (1-65535) [65535]? Percent of link stations reserved for incoming calls (0-100) [0]? Percent of link stations reserved for outgoing calls (0-100) [0]? Local SAP address (04-EC) [4]? Locally administered MAC address (hex) [40002216B00B]? Edit TG characteristics (Y)es (N)o [N]? Write this record? [Y]? y The record has been written. |
Table 13-39. Definition of TN3270E Server Under APPN
dlsb-ok APPN config>TN3270E lsadirect TN3270E config>SET TN3270E Server Parameters Enable TN3270E Server (Y/N) [Y]? TN3270E Server IP Address [9.24.104.203]? 172.16.220.2 Port Number [23]? Enable Client Address Mapping (Y/N) [N]? Default Pool name (Max 8 characters) [PUBLIC]? NetDisp Advisor Port Number [10008]? Keepalive type: 0 = none, 1 = Timing Mark, 2 = NOP [0]? Automatic Logoff (Y/N) [N]? Enable IP Precedence (Y/N) [N]? Write this record? [Y]? dlsb-ok TN3270E config>ADD/UPDATE IMPLICIT-POOL TN3270E Server Implicit Definitions Pool Name (Max 8 characters) [<DEFLT>]? Station Name (Max 8 characters) []? tnpub1 WARNING!! You are changing an existing record. LU Name Mask (Max 5 characters) [@01LU]? LU Type ( 1 - 3270 mod 2 display 2 - 3270 mod 3 display 3 - 3270 mod 4 display 4 - 3270 mod 5 display) [1]? 1 Specify LU Address Ranges (s) (y/n) [N]? Number of Implicit LUs in Pool(1-253) [5]? Write this record? [Y]? y The record has been written. |
These screens complete the definition of TN3270E server on Network Utility B.
The corresponding definition on VTAM is done like Table 13-40 below:
Table 13-40. VTAM Switched Major Node Definition
SWB1 VBUILD TYPE=SWNET TNPUB1 PU ADDR=02, X IDBLK=077, X IDNUM=221B1, X PUTYPE=2, X USSTAB=US327X, X DLOGMOD=D4C32XX3 LUB2 LU LOCADDR=02,LOGAPPL=RA03T LUB3 LU LOCADDR=03,LOGAPPL=RA03T LUB4 LU LOCADDR=04,LOGAPPL=RA03T LUB5 LU LOCADDR=05,LOGAPPL=RA03T LUB6 LU LOCADDR=06,LOGAPPL=RA03T |
After these definitions are in place, the function is ready to work on Network Utility boxes.
See Figure 13-10 for the general picture of the configuration.
Figure 13-10. TN3270E Over DLSw Subarea Connection Parameter Relationships
View figure. |
After defining the definitions above, the configuration
and its status must be monitored both on the Network Utility and VTAM
sides.
Table 13-41. Display of VTAM Screen for the LUs That We Defined in Network Utility B
D NET,ID=SWB1,E IST097I DISPLAY ACCEPTED IST075I NAME=SWB1, TYPE=SW SNA MAJ NODE 774 IST486I STATUS=ACTIV, DESIRED STATE-ACTIV IST1656I VTAMTOPO=REPORT, NODE REPORTED - YES IST084I NETWORK RESOURCES: IST089I TNPUB1 TYPE=PU_T2.1 , ACTIV IST089I LUB2 TYPE=LOGICAL UNIT , ACTIV IST089I LUB3 TYPE=LOGICAL UNIT , ACTIV IST089I LUB4 TYPE=LOGICAL UNIT , ACTIV IST089I LUB5 TYPE=LOGICAL UNIT , ACTIV IST089I LUB6 TYPE=LOGICAL UNIT , ACTIV IST314I END |
The configuration of Network Utility B can be monitored as seen
below.
Table 13-42. Display of TN3270E Server Under 'T 6'
dlsb-ok *TALK 6 Gateway user configuration dlsb-ok Config>PROTOCOL APPN dlsb-ok APPN config>TN3270E dlsb-ok TN3270E config>LIST ALL TN3270E Server Definitions TN3270E enabled: YES TN3270E IP Address: 172.16.220.2 TN3270E Port Number: 23 Default Pool Name: PUBLIC NetDisp Advisor Port Number: 10008 Client IP Address Mapping: N Keepalive type: NONE Automatic Logoff: N Timeout: 30 Enable IP Precedence: N Link Station: TNPUB1 Local Node ID: 221B1 Auto Activate: YES Host Initiated Dynamic LU Definition: NO Implicit Pool Information Pool Name: <DEFLT> Number of LUs: 5 LU Mask: @01LU LU Name NAU Addr Class Assoc LU Name Assoc NAU addr ------------------------------------------------------------------------- LUB2 2 Explicit Workstation Client IP Address Mapping ------------------------- Client IP Address Address Mask Resource Name -------------------------------------------------------------- Multiple Port -------------------------------------------------------------- PORT NUMBER ENABLE TN3270E RESOURCE NAME DISABLE FILTERING ---------- -------------- ------------- ----------------- dlsb-ok TNE3270E config> |
Table 13-43. Monitoring DLSw Connections and Sessions
(ctrl-p) dlsb-ok *TALK 5 CGW Operator Console dlsb-ok +PROTOCOL DLSW Data Link Switching Console dlsb-ok DLSw>LIST TCP SESSIONS Group/Mcast@ IP Address Conn State CST Version ACTSes SesCreates --------------------------------------------------------------------------- 1 9.24.104.203 ESTABLISHED A AIW V2RO 1 1 dlsb-ok DLSw>LIST DLSW SESSIONS ALL Source Destination State Flags Dest IP Addr Id ----------------------------------------------------------- 1 APPN 04 40002216000a04 Connected 9.24.104.203 0 |
Table 13-44. Monitoring APPN Link
dlsb-ok APPN >LIST LINK_INFORMATION Name Port Name Intf Adj CP Name Type HPR State ================================================================ TNPUB1 DLS65 65534 USIBMRA.RA03M NN INACTIVE ACT_LS 1 |
Table 13-45. Display of LU-LU connection under TN3270E
dlsb-ok APPN >TN3270E TN3270E GWCON dlsb-ok TN3270E >LIST CONNECTIONS Connection information for all the LUs Local LU Class Assoc LU Client Addr Status Prim LU SEC LU Idle Min ------------------------------------------------------------------------- @01LU6 IW 9.24.106.44 LU-LU RA03T03 LUB6 1 |
Table 13-46. Status of TN3270E Server
dlsb-ok TN3270E >LIST STATUS TN3270E Server Status Summary TN3270E IP Address: 172.16.220.2 NetDisp Advisor Port Number: 10008 Keepalive type: None Automatic Logoff: N Client IP Address mapping: N Number of Connections :1 Number of Available LUA LU's :5 Number of LUA LU's pending termination :0 Number of defined LU's :6 Number of connections in SSCP-LU state :0 Number of connections in LU-LU state :1 |
When transporting SNA, you may configure the TN3270E Server using SNA subarea links in the same 2216. With this configuration, you will need the following definitions in the host:
Table 13-47. VTAM XCA Switched Major Node Definition
X5303 VBUILD TYPE=XCA X5303PRT PORT ADAPNO=0, * CUADDR=284, * SAPADDR=4, * MEDIUM=RING X5303GRP GROUP DIAL=YES,CALL=INOUT,DYNPU=YES, * AUTOGEN=(1,L,P) |
Table 13-48. VTAM Switched Major Node: SWB1
SWB1 VBUILD TYPE=SWNET TNPUB1 PU ADDR=02, X IDBLK=077, X IDNUM=221B1, X PUTYPE=2, X USSTAB=US327X, X DLOGMOD=D4C32XX3 LUB2 LU LOCADDR=02,LOGAPPL=RA03T LUB3 LU LOCADDR=03,LOGAPPL=RA03T LUB4 LU LOCADDR=04,LOGAPPL=RA03T LUB5 LU LOCADDR=05,LOGAPPL=RA03T LUB6 LU LOCADDR=06,LOGAPPL=RA03T |
Figure 13-11. LSA SNA-Subarea for TN3270E Supporting TR/PPP Connections
View figure. |
The Switched Major Node Definitions for the TN3270E Server PUs were defined
as shown below.
Table 13-49. List of Escon Configuration
lsadirect ESCON Config>LIst Net: 4 Protocol: APPN Loopback LAN type: Token-Ring/802.5 1 APPN loopback MAC address: 40002216000B Net: 3 Protocol: LSA LAN type: Token Ring LAN number: 0 Maxdata: 2052 Loopback is enabled. MAC address: 40002216000A Block Timer: 10 ms ACK length: 10 bytes |
Now we can add APPN port, APPN link and TN3270E server definitions as seen in the following screens. If APPN and/or TN3270E packages are not loaded, refer to Table 13-36.
Table 13-50. Basic APPN CP-Name Definition
2216 Config>protocol appn 2216 APPN config>set node Enable APPN (Y)es (N)o [Y]? Network ID (Max 8 characters) [ ]? usibmra Control point name (Max 8 characters) [ ]? NN2216 Enable branch extender or border node (0=Neither, 1=Branch Extender, 2=Border Node) [0]? Route addition resistance(0-255) [128]? XID ID number for subarea connection (5 hex digits) [00000]? Use enhanced #BATCH COS (Y)es (N)o [Y]? Use enhanced #BATCHSC COS (Y)es (N)o [Y]? Use enhanced #INTER COS (Y)es (N)o [Y]? Use enhanced #INTERSC COS (Y)es (N)o [Y]? Write this record? [Y]? The record has been written. 2216 APPN config>ex 2216 Config>write Config Save: Using bank A and config number 1 2216 Config> 2216 *reload y |
Table 13-51. Adding APPN Port and Link Station
lsadirect APPN config>ADD/UPDATE PORT APPN Port Link Type: (P)PP, (FR)AME RELAY, (E)THERNET, (T)OKEN RING, (M)PC, (S)DLC, (X)25, (FD)DI, (D)LSw, (A)TM, (I)P [ ]? t Interface number(Default 0): [0]? 4 1 Port name (Max 8 characters) [T00004]? Enable APPN on this port (Y)es (N)o [Y]? Port Definition Support multiple PU (Y)es (N)o [N]? Service any node: (Y)es (N)o [Y]? High performance routing: (Y)es (N)o [N]? Maximum BTU size (768-17745) [2048]? Maximum number of link stations (1-65535) [65535]? Percent of link stations reserved for incoming calls (0-100) [0]? Percent of link stations reserved for outgoing calls (0-100) [0]? Local SAP address (04-EC) [4]? Local HPR SAP address (04-EC) [C8]? Edit TG Characteristics: (Y)es (N)o [N]? Edit LLC Characteristics: (Y)es (N)o [N]? Edit HPR defaults: (Y)es (N)o [N]? Write this record? [Y]? The record has been written. lsadirect APPN config> lsadirect APPN config> lsadirect APPN config> lsadirect APPN config> lsadirect APPN config>ADD/UPDATE LINK-STATION APPN Station Port name for the link station [ ]? T00004 Station name (Max 8 characters) [ ]? tnpub1 Activate link automatically (Y)es (N)o [Y]? MAC address of adjacent node [000000000000]? 40002216000A Solicit SSCP Session: (Y)es (N)o [N]? y Local Node ID (5 hex digits) [00000]? 221B1 Enable Host Initiated Dynamic LU Definition : (Y)es (N)o [N]? Does link support APPN function: (Y)es (N)o [Y]? n Edit TG Characteristics: (Y)es (N)o [N]? Edit LLC Characteristics: (Y)es (N)o [N]? Edit HPR defaults: (Y)es (N)o [N]? Write this record? [Y]? The record has been written. |
Table 13-52. Definition of TN3270E
lsadirect APPN config>TN3270E lsadirect TN3270E config>SET TN3270E Server Parameters Enable TN3270E Server (Y/N) [Y]? TN3270E Server IP Address [9.24.104.203]? Port Number [23]? Enable Client Address Mapping (Y/N) [N]? Default Pool name (Max 8 characters) [PUBLIC]? NetDisp Advisor Port Number [10008]? Keepalive type: 0 = none, 1 = Timing Mark, 2 = NOP [0]? Automatic Logoff (Y/N) [N]? Enable IP Precedence (Y/N) [N]? Write this record? [Y]? The record has been written. lsadirect TN3270E config>ADD/UPDATE IMPLICIT-POOL TN3270E Server Implicit Definitions Pool name (Max 8 characters) []? Station name (Max 8 characters) []? Invalid name please re-enter Station name (Max 8 characters) []? tnpub1 LU Name Mask (Max 5 characters) [@01LU]? LU Type ( 1 - 3270 mod 2 display 2 - 3270 mod 3 display 3 - 3270 mod 4 display 4 - 3270 mod 5 display) [1]? Specify LU Address Ranges(s) (y/n) [N]? Number of Implicit LUs in Pool(1-253) [1]? 5 Write this record? [Y]? |
This configuration can be monitored with similar commands as seen in "Monitoring the TN3270E Over DLSw SNA Subarea Configuration". The displayed results will also be similar.